Repository navigation
Add opt-in HTTP3, MASQUE profiles and authenticated SOCKS5 - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HTTPS proxies currently expose TCP only, while configuration subscriptions cannot discover provisioned HTTP/3 or SOCKS5 endpoints. Add independent per-host transport options and advertise their capabilities in personalized configurations.
Changes
services.https.http3: authenticated GOST MASQUE over UDP on the existing HTTPS port, TLS 1.3, HTTP Datagrams, firewall rules and the capability required for low ports. Keep the existing HTTPS/TCP and masking configuration.proxy.preferHttp3for compatible direct HTTPS profiles. Add separate MASQUE profiles only whenservices.https.masque_profilesis enabled; require HTTP/3 for that option.services.https.socks5with authenticated TCP CONNECT, UDP ASSOCIATE, bounded relay ports and validation of UTF-8 credential sizes and port conflicts. Document SOCKS5 as not recommended because it does not encrypt transport or proxy credentials.Server-side SNI chains remain HTTPS/TCP and never acquire a direct QUIC bypass. GOST 3.3.0's outbound CONNECT-UDP omits the required Extended CONNECT scheme, so this PR enables HTTP/3 on direct endpoints only. Browser API projections retain their compatible HTTPS/SOCKS5 subset.
The private inventory was updated separately as requested: HTTP/3 on
px-*, disabled oncpx-*, separate MASQUE profiles only onpx-am2, GOST HTTPS masking on every HTTPS host, and SOCKS5 disabled everywhere. No production deployment was performed; private inventory and credentials are excluded from this PR.Validation
pytest -q: 92 passed.